Ex 05 feedback #5
Conversation
|
|
||
| ;; - So suppose we define... | ||
|
|
||
| (def habitable-planets [{:pname "Earth" :moons 1} |
There was a problem hiding this comment.
Calling them habitable-planets to begin with adds a lot of confusion at line 81, where you evaluate habitable-planets and it returns the planets unchanged, which just looks like all planets are habitable.
| ;; At each re-definition, `am-i-mutable` effectively "becomes" | ||
| ;; the new _immutable_ value. | ||
| ;; | ||
| ;; "Immutable" value is actually an oxymoron. Recall, we said that |
There was a problem hiding this comment.
"Immutable" value is a tautology. "Mutable" value is an oxymoron. We can choose to use one or the other.
There was a problem hiding this comment.
Ayyo! Yes, /s/Immutable/Mutable
|
|
||
| ;; We can also alias the whole hash-map: | ||
|
|
||
| (let [add-message (fn [{:keys [pname moons] |
There was a problem hiding this comment.
These function bodies are starting to get bigger, and putting them in let blocks makes them harder to visually parse.
There was a problem hiding this comment.
Right, let's pull them out. I can do it... Should I?
There was a problem hiding this comment.
Oh you did it... I missed that. 💯
| ;; At each re-definition, `am-i-mutable` effectively "becomes" | ||
| ;; the new _immutable_ value. | ||
| ;; | ||
| ;; "Immutable" value is actually an oxymoron. Recall, we said that |
There was a problem hiding this comment.
Ayyo! Yes, /s/Immutable/Mutable
No description provided.